Known Issues or Limitations
| Service Request No. | Description |
| The Client Search Widget on the Activity screen may intermittently retain prior search criteria within the same policy session, causing fields to prepopulate instead of showing a fresh search form. | |
| In some RebalanceTransfer transactions, OIPA may intermittently throw a null pointer exception. | |
| SystematicWithdrawal setup may incorrectly show a 100% allocation validation error before allocation context initializes. | |
| Transfer assignment activities may write incorrect MoneyTypeCode to deposit tables, causing deposits with the same seed and fund but different money types to consolidate incorrectly and create valuation/deposit inconsistencies. | |
| Suspense Advanced Search may stop loading more results after the second or third scroll, even when additional matches exist preventing users from viewing all records. | |
| Checkbox fields in Program Change activities may not display in TomEE deployments. | |
| Create Suspense may stop working after a policy-level activity is created or processed, redirecting users to the Dashboard instead of Suspense. | |
| currency/money values may intermittently persist with more than two decimal places, including during activity undo/redo. These precision variances can cause downstream validation or business rule failures across multiple processing paths. | |
| Certain Suspense amounts may retain excess decimal precision, causing records to remain open even after the full amount is applied. Minor precision variances beyond two decimals can prevent Suspense from closing. | |
| The Show Hidden Funds checkbox may not work for unlocked Asset Class Models on Policy and Activity Allocation screens, preventing hidden funds from displaying when selected. | |
| Policy Values Inquiry may display values for the wrong policy number, causing searches for one policy to return another policy’s data. | |
| Processing Address Change related client activities may not update AddressLine 6 even though other address fields update. Address change details may display incorrectly until the address is manually opened and saved. | |
| Inquiry Customer Search may retain previous results instead of refreshing for the newly selected customer, causing searches to display earlier customer data. | |
| The Activity OK button may become disabled after ONLOAD or ONCHANGE events run for MultiField elements with ActionSets. | |
| When Cycle and OIPA use separate Coherence clusters, Cycle date advancement updates the database but may not refresh OIPA’s system date cache. The OIPA date remains stale until restart or manual UpdateCachedSystemDate call. | |
| Saving Client screen changes may delete hidden ASCLIENTMULTIVALUEFIELD records, causing loss of associated multi-value client data after clicking Save. | |
| The Attached Amount in the AsSuspense table may round incorrectly during suspense attachment, storing slight precision variances and causing inconsistent suspense values after processing multiple activities. |
Installation Instructions
For Installation Instructions, refer to the OIPA Release 12.2.0.0 Installation Guide on Oracle Help Center.
Click Policy Administration link at the top of the page, then click View Library for the 12.2.0.0.